Access control in new radio

ABSTRACT

A method executed by a wireless device for network access of the wireless device to a network node is disclosed. The method includes initiating an access attempt to the network node; reading a first layer of access control information (ACI) from the network node to determine whether an access control indicator in the first layer for an access category is ON, wherein the access control indicator for the access category is associated with a characteristic/classification of the access attempt by the wireless device to the network node; in response to the access control indicator in the first layer for the access category being ON, reading a second layer of the ACI from the network node to determine whether the access attempt to the network node is allowed based on one or more specific parameters associated with the access category in the second layer of the ACI.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This is a divisional of application Ser. No. 15/942,505, filed Mar. 31,2018, which claims priority from provisional application Ser. No.62/480,512, filed Apr. 2, 2017; the contents of all above-namedapplications are fully incorporated herein by reference for allpurposes.

The present application claims the benefit of and priority to aprovisional U.S. patent application Ser. No. 62/480,512 filed Apr. 2,2017, entitled “ACCESS CONTROL IN NEW RADIO,” (hereinafter referred toas “US62,068 application”). The disclosure of the US62,068 applicationis hereby incorporated fully by reference into the present application.

FIELD

The present disclosure generally relates to wireless communicationmethods and systems, and more particularly, to access control for thenext generation wireless communication networks.

BACKGROUND

The 3^(rd) Generation Partnership Project (3GPP) is currently developingprotocols for the next generation wireless communication networks, alsoreferred to as New Radio (NR). NR will enable new use cases for cellularaccess, and also increase the capacity for existing data applications.Even though the capacity of a system under NR may increase, there stillcan be situations where the base stations (e.g., next generation node Bs(gNBs)) and/or core networks (CNs) of the system may become overloaded.For example, a system overload may occur when a large number of userequipments (UEs) try to access the system in a synchronized manner(e.g., at the same time).

In a fourth generation (4G) wireless network, such as long termevolution (LTE), evolved LTE (eLTE), or LTE-Advanced (LTE-A), a radioaccess network (RAN) is responsible for activating access control whenthe RAN or the CN is overloaded. For example, a current access controlscheme under a 4G wireless network may be performed in the RAN (e.g.,RAN based), which primarily bars low priority UEs from attempting toperform random access procedures to transition from RRC_IDLE state toRRC_CONNECTED state. That is, the low priority UEs can be barred by theRAN from accessing the wireless network for a predetermined period oftime when the RAN or CN is overloaded.

Based on the current 3GPP standard discussion, in addition to thecurrent RRC_CONNECTED and RRC_IDLE states, a new RRC state, RRC_INACTIVEstate, is introduced in the NR wireless networks. RRC_INACTIVE stateunder an NR wireless network is configured by a base station (e.g.,gNB), and may be invisible to the CN. For example, when a base station(e.g., gNB) suspends a UE from RRC_CONNECTED to RRC_INACTIVE state, theCN may not receive a notification of such, and may still consider the UEas in RRC_CONNECTED state. While in RRC_INACTIVE state, the UE maytransfer uplink (UL) data to the base state (e.g., gNB) withoutundergoing RRC state transition (e.g., without transitioning fromRRC_INACTIVE state to RRC_CONNECTED state).

In the legacy 4G wireless networks, when the CN is overloaded and sendsinstructions to the RANs to block or bar traffic, the RANs may set upbarring parameters to bar or block RRC_IDLE UEs from performing RRCstate transition to RRC_CONNECTED state for data transmission. However,the access control schemes under the 4G wireless networks do not takeinto account of the newly introduced RRC_INACTIVE UEs that are capableof direct data uplink transmission to the base station withouttransitioning into RRC_CONNECTED state. As such, the legacy 4G wirelessnetworks cannot effectively treat the RRC_INACTIVE UEs when the basestation and/or the CN is overloaded.

For example, if RRC_INACTIVE UEs are present in a wireless network, andthe CN does not know that some UEs under the RAN are suspended in theRRC_INACTIVE state (e.g., temporarily do not have data to upload), theCN may underestimate the network traffic condition in the RANs becauseof the presence of the RRC_INACTIVE UEs. That is, the CN may considerthe RRC_INACTIVE UEs are in the RRC_CONNECTED state, and use theircurrent data rates for the network traffic estimate. However, when theseRRC_INACTIVE UEs start transferring data (e.g., using 2-step or 4-stepRACH procedure) to their base stations, the actual data traffic would begreater than what the CN had originally estimated (e.g., the RANcontinues to bring in additional traffic from the RRC_INACTIVE UEs tothe CN), thereby exacerbating the traffic condition and overloading thebase stations and/or the CN.

Thus, there is a need in the art for access control in new radiowireless networks to block traffic by dynamically assigning accesscontrol categorizations and sub-categorizations (e.g., barring factors)based on traffic conditions, to take into account of and manage each ofthe RRC states in NR, to conserve radio resources (e.g., stopunnecessary consumption of radio resource), and to preserve base stationand/or CN's processing capacity for high priority traffic, data and/orapplications from specific UEs.

SUMMARY

The present disclosure is directed to access control in new radio.

In a first aspect, a method for network access of a wireless device(e.g., a UE) to a network node (e.g., a base station) is disclosed, Themethod comprises initiating an access attempt to the network node;reading a first layer of access control information (ACI) from thenetwork node to determine whether an access control indicator in thefirst layer for an access category is ON, wherein the access controlindicator for the access category is associated with acharacteristic/classification of the access attempt by the wirelessdevice to the network node; in response to the access control indicatorin the first layer for the access category being ON, reading a secondlayer of the ACI from the network node to determine whether the accessattempt to the network node is allowed based on one or more specificparameters associated with the access category in the second layer ofthe ACI.

In an implementation of the first aspect, the method further comprisesreceiving an access attempt configuration (AAC) from the network node,the AAC including at least one value tag corresponding to the accesscategory.

In another implementation of the first aspect, the method furthercomprises performing a value tag check to determine whether there is anupdate associated with the access category.

In another implementation of the first aspect, when the at least onevalue tag has not been updated, using the AAC to determine whether theaccess attempt to the network node is allowed.

In another implementation of the first aspect, the method furthercomprises, when the at least one value tag has been updated, using thesecond layer of the ACI to determine whether the access attempt to thenetwork node is allowed based on the one or more specific parametersassociated with the access category in the second layer of the ACI.

In another implementation of the first aspect, the AAC is configured bythe network node, and includes information of at least one of thewireless device's access class and the ACI's default and currentsettings.

In another implementation of the first aspect, the wireless device'saccess class is dynamically assigned by the network node based on atleast one of the wireless device's ID, quality of service (QoS)requirement and data size.

In another implementation of the first aspect, the method furthercomprises, in response to the access control indicator in the firstlayer for the access category being OFF, performing an access procedureto gain access to the network node without reading the second layer ofthe ACI.

In another implementation of the first aspect, the first layer of theACI is categorized based on a radio resource control (RRC) state of thewireless device, and includes access control indications and commonparameters.

In another implementation of the first aspect, the wireless device makesthe access attempt in one of RRC_Inactive state, RRC_Connected state,and RRC_Idle state.

In another implementation of the first aspect, the first layer of ACI isbroadcasted by the network node through minimum system information.

In another implementation of the first aspect, the method furthercomprises in response to the access control indicator in the first layerfor the access category being ON, requesting the second layer of the ACIby the wireless device from the network node when the at least one valuetag has been updated; sending, by the network node, the second layer ofthe ACI to the wireless device in response to the request through othersystem information.

In another implementation of the first aspect, the access category isassociated with at least one of random access procedure, RAN-basednotification area (RNA), RRC state transition, applications, networkslice, RAN slice, quality of service (QoS) requirement and data size.

In another implementation of the first aspect, the access category isRNA update such that the RNA update is controlled by the ACI.

In a second aspect, a wireless device (e.g., a UE) for network access ofthe wireless device to a network node (e.g., a base station) isdisclosed. The wireless device comprises: one or more processors; anon-transitory machine-readable memory storing a program, the programexecutable by at least one of the one or more processors, the programcomprising sets of instructions for: initiating an access attempt to thenetwork node; reading a first layer of access control information (ACI)from the network node to determine whether an access control indicatorin the first layer for an access category is ON, wherein the accesscontrol indicator for the access category is associated with acharacteristic/classification of the access attempt by the wirelessdevice to the network node; in response to the access control indicatorin the first layer for the access category being ON, reading a secondlayer of the ACI from the network node to determine whether the accessattempt to the network node is allowed based on one or more specificparameters associated with the access category in the second layer ofthe ACI.

In an implementation of the second aspect, the program further comprisesthe sets of instructions for receiving an access attempt configuration(AAC) from the network node, the AAC including at least one value tag,the at least one value tag corresponding to the access category.

In another implementation of the second aspect, the program furthercomprises the sets of instructions for performing a value tag check todetermine whether there is an update associated with the accesscategory.

In another implementation of the second aspect, when the at least onevalue tag has not been updated, using the AAC to determine whether theaccess attempt to the network node is allowed.

In another implementation of the second aspect, the program furthercomprises the sets of instructions for, when the at least one value taghas been updated, using the second layer of the ACI to determine whetherthe access attempt to the network node is allowed based on the one ormore specific parameters associated with the access category in thesecond layer of the ACI.

In another implementation of the second aspect, the AAC is configured bythe network node, and includes information of at least one of thewireless device's access class and the ACI's default and currentsettings.

In another implementation of the second aspect, the wireless device'saccess class is dynamically assigned by the network node based on atleast one of the wireless device's ID, quality of service (QoS)requirement and data size.

In another implementation of the second aspect, the program furthercomprises the sets of instructions for, in response to the accesscontrol indicator in the first layer for the access category being OFF,performing an access procedure to gain access to the network nodewithout reading the second layer of the ACI.

In another implementation of the second aspect, the first layer of theACI is categorized based on a radio resource control (RRC) state of thewireless device, and includes access control indications and commonparameters.

In another implementation of the second aspect, the wireless devicemakes the access attempt in one of RRC_Inactive state, RRC_Connectedstate, and RRC_Idle state.

In another implementation of the second aspect, the program furthercomprises the sets of instructions for, in response to the accesscontrol indicator in the first layer for the access category being ON,requesting the second layer of the ACI by the wireless device from thenetwork node when the at least one value tag has been updated.

In a third aspect, a network node (e.g., a base station) for networkaccess of a wireless device (e.g., a UE) to the network node isdisclosed. The network node comprises: one or more processors: anon-transitory machine-readable memory storing a program, the programexecutable by at least one of the one or more processors, the programcomprising sets of instructions for: providing a first layer of accesscontrol information (ACI) to the wireless device, the first layer of theACI having one or more access control indicators corresponding to one ormore access categories; providing a second layer of the ACI to thewireless device upon request; wherein the wireless device requests forthe second layer of the ACI when at least one of the one or more accesscontrol indicators in the first layer of the ACI associated with acharacteristic/classification of an access attempt by the wirelessdevice to the network node is ON.

In an implementation of the third aspect, the program further comprisesthe sets of instructions for providing an access attempt configuration(AAC) to the wireless device, the AAC including at least one value tagcorresponding to the access category.

In another implementation of the third aspect, the network nodedynamically assigns the wireless device's access class based on at leastone of the wireless device's ID, quality of service (QoS) requirementand data size.

In another implementation of the third aspect, the access category isassociated with at least one of random access procedure, RAN-basednotification area (RNA), RRC state transition, applications, networkslice, RAN slice, quality of service (QoS) requirement and data size.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of UEs performing data transmission using2-step or 4-step random access procedures in a next generation wirelessnetwork, according to an exemplary implementation of the presentapplication.

FIG. 2 is a diagram illustrating data transmission using a 2-step randomaccess procedure, according to an exemplary implementation of thepresent application.

FIG. 3 is a diagram illustrating data transmission using a 4-step randomaccess procedure, according to an exemplary implementation of thepresent application.

FIG. 4 is a diagram illustrating an access control information (ACI)structure, according to an exemplary implementation of the presentapplication.

FIG. 5 is a flowchart illustrating a method for access control,according to an exemplary implementation of the present application.

FIG. 6A is a diagram illustrating an access attempt configuration (AAC)transmission for an RRC_INACTIVE UE, according to an exemplaryimplementation of the present application.

FIG. 6B is a diagram illustrating an access control information (ACI)transmission for an RRC_INACTIVE UE, according to an exemplaryimplementation of the present application.

FIG. 7A is a diagram illustrating an access attempt configuration (AAC)transmission for an RRC_CONNECTED UE, according to an exemplaryimplementation of the present application.

FIG. 7B is a diagram illustrating an access control information (ACI)transmission for an RRC_CONNECTED UE, according to an exemplaryimplementation of the present application.

FIG. 8 illustrates a block diagram of a node for wireless communication,according to various aspects of the present application.

DETAILED DESCRIPTION

The following description contains specific information pertaining toexemplary embodiments in the present disclosure. The drawings in thepresent disclosure and their accompanying detailed description aredirected to merely exemplary embodiments. However, the presentdisclosure is not limited to merely these exemplary embodiments. Othervariations and embodiments of the present disclosure will occur to thoseskilled in the art. Unless noted otherwise, like or correspondingelements among the figures may be indicated by like or correspondingreference numerals. Moreover, the drawings and illustrations in thepresent disclosure are generally not to scale, and are not intended tocorrespond to actual relative dimensions.

The following description contains specific information pertaining toexemplary implementations in the present disclosure. The drawings in thepresent disclosure and their accompanying detailed description aredirected to merely exemplary implementations. However, the presentdisclosure is not limited to merely these exemplary implementations.Other variations and implementations of the present disclosure willoccur to those skilled in the art. Unless noted otherwise, like orcorresponding elements among the figures may be indicated by like orcorresponding reference numerals. Moreover, the drawings andillustrations in the present disclosure are generally not to scale, andare not intended to correspond to actual relative dimensions.

For the purpose of consistency and ease of understanding, like featuresare identified (although, in some examples, not shown) by numerals inthe exemplary figures. However, the features in differentimplementations may be differed in other respects, and thus shall not benarrowly confined to what is shown in the figures.

The description uses the phrases “in one implementation,” or “in someimplementations,” which may each refer to one or more of the same ordifferent implementations. The term “coupled” is defined as connected,whether directly or indirectly through intervening components, and isnot necessarily limited to physical connections. The term “comprising,”when utilized, means “including, but not necessarily limited to”; itspecifically indicates open-ended inclusion or membership in theso-described combination, group, series and the equivalent.

In some implementations, the present application may include thelanguage, such as, “at least one of [element A] and [element B]”. Thislanguage may refer to one or more of the elements. For example, “atleast one of A and B” may refer to “A”, “B”, or “A and B”. In someimplementations, the present application may include the language, suchas, “[element A], [element B], and/or [element C].” This language mayrefer to either of the elements or any combination thereof. In otherwords, “A, B, and/or C” may refer to “A”, “B”, “C”, “A and B”, “A andC”, “B and C”, or “A, B, and C”.

Additionally, for the purposes of explanation and non-limitation,specific details, such as functional entities, techniques, protocols,standard, and the like are set forth for providing an understanding ofthe described technology. In other examples, detailed description ofwell-known methods, technologies, system, architectures, and the likeare omitted so as not to obscure the description with unnecessarydetails.

Persons skilled in the art will immediately recognize that any networkfunction(s) or algorithm(s) described in the present disclosure may beimplemented by hardware, software or a combination of software andhardware. Described functions may correspond to modules may be software,hardware, firmware, or any combination thereof. The softwareimplementation may comprise computer executable instructions stored oncomputer readable medium such as memory or other type of storagedevices. For example, one or more microprocessors or general purposecomputers with communication processing capability may be programmedwith corresponding executable instructions and carry out the describednetwork function(s) or algorithm(s). The microprocessors or generalpurpose computers may be formed of applications specific integratedcircuitry (ASIC), programmable logic arrays, and/or using one or moredigital signal processor (DSPs). Although some of the exemplaryimplementations described in this specification are oriented to softwareinstalled and executing on computer hardware, nevertheless, alternativeexemplary implementations implemented as firmware or as hardware orcombination of hardware and software are well within the scope of thepresent disclosure.

The computer readable medium includes but is not limited to randomaccess memory (RAM), read only memory (ROM), erasable programmableread-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM), flash memory, compact disc read-only memory (CD ROM),magnetic cassettes, magnetic tape, magnetic disk storage, or any otherequivalent medium capable of storing computer-readable instructions.

A radio communication network architecture (e.g., a long term evolution(LTE) system, an LTE-Advanced (LTE-A) system, or an LTE-Advanced Prosystem) typically includes at least one network node (e.g., basestation), at least one user equipment (UE), and one or more optionalnetwork elements that provide connection towards a network. The UEcommunicates with the network (e.g., a core network (CN), an evolvedpacket core (EPC) network, an Evolved Universal Terrestrial Radio Accessnetwork (E-UTRAN), a Next-Generation Core (NGC), or an internet),through a radio access network (RAN) established by the network node(e.g., base station).

It should be noted that, in the present application, a UE may include,but is not limited to, a mobile station, a mobile terminal or device, auser communication radio terminal. For example, a UE may be a portableradio equipment, which includes, but is not limited to, a mobile phone,a tablet, a wearable device, a sensor, or a personal digital assistant(PDA) with wireless communication capability. The UE is configured toreceive and transmit signals over an air interface to one or more cellsin a radio access network.

A network node may include a base station. A base station may include,but is not limited to, a node B (NB) as in the UMTS, an evolved node B(eNB) as in the LTE-A, a radio network controller (RNC) as in the UMTS,a base station controller (BSC) as in the GSM/GERAN, a ng-eNB as in anE-UTRA base station in connection with the 5GC, a next generation node B(gNB) as in the 5G-AN, and any other apparatus capable of controllingradio communication and managing radio resources within a cell. The basestation may connect to serve the one or more UEs through a radiointerface to the network.

A base station may be configured to provide communication servicesaccording to at least one of the following radio access technologies(RATs): Worldwide Interoperability for Microwave Access (WiMAX), GlobalSystem for Mobile communications (GSM, often referred to as 2G), GSMEDGE radio access Network (GERAN), General Packet Radio Service (GRPS),Universal Mobile Telecommunication System (UMTS, often referred to as3G) based on basic wideband-code division multiple access (W-CDMA),high-speed packet access (HSPA), LTE, LTE-A, eLTE (evolved LTE), NewRadio (NR, often referred to as 5G), and/or LTE-A Pro. However, thescope of the present application should not be limited to the abovementioned protocols.

The base station is operable to provide radio coverage to a specificgeographical area using a plurality of cells forming the radio accessnetwork. The base station supports the operations of the cells. Eachcell is operable to provide services to at least one UE within its radiocoverage. More specifically, each cell (often referred to as a servingcell) provides services to serve one or more UEs within its radiocoverage, (e.g., each cell schedules the downlink and optionally uplinkresources to at least one UE within its radio coverage for downlink andoptionally uplink packet transmissions). The base station cancommunicate with one or more UEs in the radio communication systemthrough the plurality of cells. A cell may allocate sidelink (SL)resources for supporting proximity service (ProSe). Each cell may haveoverlapped coverage areas with other cells.

As discussed above, the frame structure for NR is to support flexibleconfigurations for accommodating various next generation (e.g., 5G)communication requirements, such as enhanced mobile broadband (eMBB),massive machine type communication (mMTC), ultra reliable communicationand low latency communication (URLLC), while fulfilling highreliability, high data rate and low latency requirements. The orthogonalfrequency-division multiplexing (OFDM) technology as agreed in 3GPP mayserve as a baseline for NR waveform. The scalable OFDM numerology, suchas the adaptive sub-carrier spacing, the channel bandwidth, and theCyclic Prefix (CP) may be also used. Additionally, two coding schemesare considered for NR: (1) low-density parity-check (LDPC) code and (2)Polar Code. The coding scheme adaption may be configured based on thechannel conditions and/or the service applications.

Moreover, it is also considered that in a transmission time interval TXof a single NR frame, a downlink (DL) transmission data, a guard period,and an uplink (UL) transmission data should at least be included, wherethe respective portions of the DL transmission data, the guard period,the UL transmission data should also be configurable, for example, basedon the network dynamics of NR. In addition, sidelink resource may alsobe provided in an NR frame to support ProSe services.

FIG. 1 shows a schematic diagram of UEs performing data transmissionusing 2-step and 4-step random access procedures in a next generation(e.g., 5G NR) wireless network, according to an exemplary implementationof the present application. As shown in FIG. 1, wireless communicationsystem 100 includes UE 102 a, UE 102 b, base station 104 a (e.g., a gNB)having coverage area 106 a, base station 104 b (e.g., a gNB) havingcoverage area 106 b, where base stations 104 a and 104 b can access corenetwork (CN) 108, such as a next generation core network (e.g., 5G CoreNetwork (5GC)). In the present implementation, CN 108 may signal basestation 104 a and base station 104 b through 5GC notifications. In theone implementation, base station 104 a is within a first RAN-basednotification area, RNA1, while base station 104 b is within a secondRAN-based notification area, RNA2, that is different from RNA1. In thepresent exemplary implementation, RNA1 and RNA2 are neighboringRAN-based notification areas. In another implementation, base stations104 a and 104 b may be two neighboring cells in a single RAN-basednotification area. In FIG. 1, UEs 102 a and 102 b can each use a 2-stepor a 4-step random access procedure to establish connection orre-synchronization with their respective base stations 104 a and 104 b.Also, UEs 102 a and 102 b are capable of transmitting uplink (UL) datato their respective base stations 104 a and 104 b using the 2-step or4-step random access procedure.

FIG. 2 illustrates a diagram of data transmission using a 2-step randomaccess procedure, according to an exemplary implementation of thepresent application. Diagram 200 includes UE 202 and base station 204(e.g., a gNB) where UE 202 may transmit UL data to base station 204using a 2-step random access procedure. In the present implementation,UE 202 and base station 204 may substantially correspond to UE 102 a (orUE 102 b) and base station 104 a (or base station 104 b), respectively,in FIG. 1.

As illustrated in FIG. 2, action 210 includes UE 202 transmitting arandom access channel (RACH) preamble (e.g., MSG 1) to base station 204.Base station 204 configures random access channel (RACH) resources whichare used to let UE 202 transmit the RACH preamble, uplink (UL) data andthe UE ID of UE 202. UE 202 may randomly select a RACH preamble resourceto be actually used from the RACH preamble resources (e.g., prescribedby combinations of time resources, frequency resources and sequenceresources). Then, UE 202 may transmit the RACH preamble using theselected RACH preamble resource. The UL data along with the UE ID of UE202 may also be multiplexed with the RACH preamble in the MSG1.

As illustrated in FIG. 2, action 212 includes base station 204transmitting a random access response (RAR) (e.g., MSG 2) to UE 202,when base station 204 detects the RACH preamble, the UL data along withthe UE ID of UE 202. For UL data transmission, base station 204 mayprovide an acknowledge (ACK)/non-acknowledgement (NACK) message in MSG 2to indicate whether base station 204 has received the UL data in MSG 1successfully.

FIG. 3 illustrates a diagram of data transmission using a 4-step randomaccess procedure, according to an exemplary implementation of thepresent application. Diagram 300 includes UE 302 and base station 304(e.g., a gNB), where UE 302 may transmit UL data to base station 304using a 4-step random access procedure. In the present implementation,UE 302 and base station 304 may substantially correspond to UE 102 a (orUE 102 b) and base station 104 a (or base station 104 b), respectively,in FIG. 1.

As illustrated in FIG. 3, action 310 includes UE 302 transmitting arandom access channel (RACH) preamble (e.g., MSG 1) to base station 304.In the present implementation, UE 302 may randomly select a RACHpreamble resource to be actually used from a group of RACH preambleresource candidates (prescribed by combinations of time resources,frequency resources and sequence resources). Then, UE 302 may transmitthe RACH preamble using the selected RACH preamble resource.

Action 312 includes base station 304 transmitting a random accessresponse (RAR) (e.g., MSG 2) to UE 302, when base station 304 detectsthe RACH preamble. The RAR is transmitted over the entire cell coveredby base station 304, since base station 304 may not have been able toidentified UE 302 that transmitted the RACH preamble. For example, aphysical downlink shared channel (PDSCH) resource in which the RAR ismapped may be indicated by base station 304 to UE 302 via a physicaldownlink control channel (PDCCH). Also, the RAR may contain informationrelating to a resource to be used by UE 302 in uplink or informationrelating to uplink transmission timing for UE 302.

Action 314 includes UE 302 transmitting an RRC connection request or ascheduling request (e.g., MSG 3) using the uplink resource specified bybase station 304 via the RAR in action 312. In the presentimplementation, UE 302 transmits a Resume Request message to basestation 304, where the Resume Request message may not be requesting fortransitioning to RRC_CONNECTED state. Instead, the Resume Requestmessage in MSG 3 is used for transmitting uplink (UL) data.

Action 316 includes base station 304 transmitting an RRC connectionresponse or a scheduling response (e.g., MSG 4) to UE 302, when basestation 304 detects the RRC connection request or the schedulingrequest. In the present implementation, base station 304 transmits aResume Response message to UE 302, where the Resume Response message maynot be for resuming, but contains corresponding acknowledgement of theUL data sent in MSG 3 in action 314.

Thus, FIGS. 2 and 3 show that according implementations of the presentapplication, UEs can transmit UL data to their respective base stations(e.g., gNBs) in a 5G NR wireless network using either a 2-step or 4-steprandom access procedure. For example, UE 202 (or UE 302) may be inRRC_INACTIVE state, and still able to transmit UL data to base station204 (or 304) without transitioning to RRC_CONNECTED state.

FIG. 4 is a diagram illustrating an access control information (ACI)structure, according to an exemplary implementation of the presentapplication. ACI structure 400 may include a plurality of layers. In thepresent implementation, ACI structure 400 includes a first layer (e.g.,Layer 1) and a second layer (e.g., Layer 2). Layer 1 of ACI structure400 includes access control indications and common parameters for eachof a plurality of groups (e.g., Group 1 and Group 2). Layer 2 of ACIstructure 400 includes sub-categorizations of the access control relatedinformation for each group (e.g., based on RRC state) in Layer 1. Forexample, the sub-categorizations in Layer 2 may be based on thecharacteristics of the access attempts by the UEs. Although FIG. 4illustrates that ACI structure 400 includes two layers, it should beunderstood that ACI structure 400 may include more than two layers. Themulti-layer ACI structure 400 allows the next generation (e.g., 5G NR)wireless network to achieve smaller granularity on controlling accessattempt.

In the present implementation, Layer 1 of ACI structure 400 is dividedinto a plurality of groups based on RRC state. For example, in Layer 1,Group 1 is categorized by RRC_CONNECTED state, while Group 2 iscategorized by RRC_INACTIVE state. It should be noted that another group(e.g., Group 3 not explicitly shown in FIG. 4) may be categorized byRRC_IDLE state in ACI structure 400. As illustrated in FIG. 4, eachgroup contains one or more access control indication(s) and accesscontrol parameter(s). For example, in Group 1, the access controlindications for RRC_CONNECTED state may include, but is not limited to,access control ON/OFF indicators for the correspondingsub-categorizations in Layer 2, value tags for the correspondingsub-categorizations in Layer 2, and sub-categorization mapping of Layer2.

The access control ON/OFF indicators in Layer 1 of ACI structure 400 mayprovide indication to the UEs on whether a current access control is ONor OFF for a corresponding sub-categorization in Layer 2. In oneimplementation, the access control ON/OFF indicators may be in the formof a bit map.

The value tags in Layer 1 of ACI structure 400 may provide indication tothe UEs on whether the access control parameters for each group and/orsub-categorization have been updated. In one implementation, beforereceiving ACI structure 400, the UE may receive a value tag through amessage from the base station (e.g., gNB) in a message containing accesscontrol configuration (AAC). If later, when reading the value tag inLayer 1, the UE determines the value tag is the same as the one in theACC, then the UE already has the information. Thus, there is no need forthe base station to broadcast or transmit (or for the UE to read) theinformation again. In another implementation, the UE may not receive avalue tag in the message containing the AAC from the base station. Thatis, the UE may not receive the current ACI setting in the messagecontaining the AAC. In such case, the UE still performs value tag checkupon receiving Layer 1 of the ACI structure, but compares the value tagin Layer 1 of the ACI structure with the value tag that the UE hadpreviously read and stored. In both implementations described above, theUE performs value tag check before requesting Layer 2 of the ACIstructure. Reading value tags before reading the specific parameters forthe corresponding sub-categorization in Layer 2 can avoid unnecessaryACI reading overhead, when the value tag has not been changed orupdated. The access control indications and parameters within eachgroup, layer and sub-categorization of ACI structure 400 can be updatedindependently.

The sub-categorization mapping in Layer 1 of ACI structure 400 mayprovide information (e.g., a tree-type mapping) to the UEs to let theUEs know the details (e.g., default and/or current settings) of ACIstructure 400. As such, the UEs can find and read the correspondingsub-categorizations without any prior knowledge of the ACI structure400. For example, all of the details in Layer 2 of ACI structure 400 maybe included in the sub-categorization mapping.

In each group, the access control parameters for an RRC state mayinclude, but is not limited to, allowed access time duration, dataretransmission times, time/frequency resources for data transmission,barring factor and backoff timer. In one implementation, the accesscontrol parameters may be common parameters that all of the UEs need toread from the base station. The common parameters may include parametersthat are needed by all UEs within each RRC state and/or the parameter'sassociated settings are the same for each sub-categorization.

In each group the indicators for an RRC state may include, but is notlimited to, access control ON/OFF indicators for the correspondingsub-categorizations (e.g., access classes) in Layer 2, value tags forthe corresponding sub-categorizations (e.g., access classes) in Layer 2,and sub-categorization mapping of Layer 2.

As shown in FIG. 4, Layer 2 includes sub-categorizations of the accesscontrol related information based on the one or more characteristics ofthe access attempts of the UEs. The characteristics of the accessattempt may include, but are not limited to, 2-step or 4-step randomaccess channel perspective, same RNA (e.g., home RAN) or different RNA,RRC state transition, applications, network slice, RAN slice, QoSrequirement and mobility. For example, when a next generation (e.g., 5GNR) wireless network is congested or having limited resource, the UEswith high QoS/application requirements may be given precedence overother UEs in radio resource assignment. It should be noted, ACIstructure 400 is forward compatible. That is, ACI structure 400 may addor hook new messages and/or parameters in its layered structure to becompatible with future access control structures, schemes and methods.

As shown in FIG. 4, the characteristic of the access attempt for Group 1(e.g., RRC_CONNECTED state) may be based on core network slice, RANslice, and the QoS requirement of the UEs for Layer 2. For example,there is a specific parameter set (e.g., specific parameter sets 1, 2, .. . n) for each QoS requirement (e.g., QoSs 1, 2, . . . n). Thecharacteristics of the access attempt for Group 2 (e.g., RRC_INACTIVEstate) may be based on core network slice, RAN slice, and 2-step or4-step random access procedures for Layer 2. For example, there is aspecific parameter set (e.g., specific parameter sets 1, 2, . . . n) foreach of the characteristics. It should be noted that the next generationwireless network may assign and configure independent sets of accesscontrol parameters for different application(s)/QoS(s) via differentsub-categorizations.

As shown in FIG. 4, ACI structure 400 include multiple groups based onRRC state, where each group includes at least two layers. Within eachgroup of ACI structure 400, Layer 1 includes common parameters, whileLayer 2 includes specific-parameters for each sub-categorization. In oneimplementation, the access control parameters may be common parametersthat all of the UEs need to read from the base station. For example, thecommon parameters may include parameters that are needed by all UEswithin each RRC state and the parameter's associated settings are thesame for each sub-categorization. The specific parameters are theparameters which associated settings are different between eachsub-categorization and can be: allowed time duration, dataretransmission times, time/frequency resources for data transmission,two or four steps random access channels perspective, barring factor,backoff timer. It is noted that the specific parameters also can bedifferent for each sub-categorization. ACI structure 400, as a spanningtree structure shown in the FIG. 4, is merely an example of the presentapplication, as all of the access control parameters can be combined,exchanged, replaced and be used in each layers.

ACI structure 400 may contain a lot of information, but not all of theinformation is needed by every UE trying to access the NR wirelessnetwork. According to implementations of the present application, notall UEs need to read the entire ACI structure. That is, the UEs needonly the parts of the ACI structure that pertain to them. Each group,layer and/or sub-categorization of the ACI structure can be transmittedor broadcasted separately by using different messages and/or throughdifferent network entities (e.g., base stations and/or transmit receivepoints (TRPs)). For example, a central node receives the system request,it can instruct a TRP under the central node to transmit thesub-categorization.

Layer 1 of ACI structure 400 may further include indicators to indicatethe necessary/required information to the UEs for receiving associatedsub-categorization in Layer 2 of ACI structure 400. Thenecessary/required information indicators may include, but is notlimited to, sub-categorization mapping, time/frequency resource used fortransmission, the network entity and/or system information by which eachsub-categorization is transmitted or broadcasted. Hence, a UE can readonly the part of the ACI it needs accordingly.

Layer 1 of ACI structure 400 can contain access control ON/OFFindicators for indicating whether an access control scheme is currentlyON or OFF for each sub-categorization (can be a bitmap). Layer 1 of ACIstructure 400 can also contain value tags for indicating the updatedversion of access control parameters for each group and/or eachsub-categorization. The indicator(s) and parameter(s) within each group,layer and sub-categorization of ACI can be updated independently. Thesub-categorizations are determined based on a need basis (e.g., based oncurrent traffic condition).

Based on the resource allocation and the supported service a basestation or TRP provides, the base station or TRP can periodicallybroadcast Layer 1 of ACI structure 400, and transmit or broadcast Layer2 of ACI structure 400 when requested by the UEs (e.g., on-demandbasis). In one implementation, Layer 1 of ACI structure 400 is containedor carried in minimal system information (SI), periodically broadcastedby the base station or TRP. Also, the base station or TRP may transmitdedicated RRC signaling and/or broadcast Layer 2 of ACI structure 400 toindividual UEs when such requests are received from the UEs, where Layer2 of ACI structure 400 is contained or carried in other SI. It should benoted that ACI structure 400 may become invalid when a UE moves out ofthe base station's coverage area (e.g., moving out of an NR network intoan LTE network), then the UE may adopt the corresponding access controlin accordance with the LTE specification.

According to an implementation of the present application, a basestation (e.g., gNB) may perform beamforming, and use different beams tobroadcast different ACI structures subject to different access controlschemes. A UE may need to perform ACI acquisition for every beam fromthe base station. In another implementation, all beams formed andbroadcasted by the base station may have a uniform ACI structure. A UEmay skip ACI acquisition when the UE changes from one beam to anotherbeam. For example, when a UE performs beam recovery, it can apply thesame parameters acquired from the previous beam, when switching toanother beam under the same cell.

According to an implementation of the present application, a basestation may use medium access control (MAC) control element (CE) or RRCsignaling to request connected UEs to perform ACI acquisition, to changeany of the access control ON/OFF indicators in Layer 1 or modify thespecific parameters in Layer 2. In another implementation, forRRC_INACTIVE UEs, a base station can use paging message to trigger whichkind of behavior it desires.

FIG. 5 is a flowchart illustrating a method for access control,according to an exemplary implementation of the present application.Flowchart 500 starts with action 580 and ends with action 599. In action582, a UE receives access attempt configuration. Depending on the RRCstate the UE is in, the UE may receive the AAC in different RRC messagesfrom a base station on which the UE camps. The AAC may be UE-specific,meaning that the AAC is configured by the base station and may containthe UE's access class(es) (e.g., sub-categorization), which RACH (e.g.,2-step or 4-step or both) is allowed for the UE for each correspondingaccess attempt purpose, and etc. In one implementation of the presentapplication, the AAC may be determined by, for example, the applicationthe UE performs and its associated QoS requirement. In addition, thecurrent corresponding specific parameters in Layer 2 of an ACI structure(e.g., Layer 2 of ACI structure 400 in FIG. 4) for the UE can also becontained in the RRC message or ACC for each access attempt purpose.

In action 584, the UE may generate an access attempt. Depending on theRRC state the UE is in, the UE may generate an access attempt forvarious access attempt purposes, such as data transmission via randomaccess, RAN notification area (RNA) update, and RRC resume procedure. Inaction 586, after the UE generates an access attempt, the UE may readLayer 1 of the ACI structure (e.g., Layer 1 of ACI structure 400 in FIG.4) broadcasted by the base station. For example, the UE may checkwhether the access control ON/OFF indicators for its correspondingsub-categorizations are ON or OFF by reading the access control ON/OFFindicators within Layer 1 of the ACI structure. The Layer 1 of the ACIstructure may be included in the minimal SI or periodically broadcastedSI from the base station.

In action 588, the UE may check whether the access control ON/OFFindicator(s) for the corresponding sub-categorization(s) is ON or OFF.If the access control ON/OFF indicator for a correspondingsub-categorization is OFF, the UE may stop reading or ignore theassociated control parameters within Layer 2 of the ACI structure. Ifthe access control ON/OFF indicator for the correspondingsub-categorization is OFF, the UE may also stop reading or ignore thecommon parameters in Layer 1 of the ACI structure. The UE may proceed toaction 598 to perform access procedure. On the other hand, if the accesscontrol ON/OFF indicator for a corresponding sub-categorization is ON,the UE needs to further read the associated control parameters withinLayer 2 of the ACI structure (which obtained via other SI or dedicatedsignaling or on-demand broadcast SI or on-demand other SI) to obtain allaccess control parameters it needs to apply.

Before the UE obtaining Layer 2 of the ACI structure, the UE may checkthe value tag of corresponding sub-categorization in Layer 2 in action590. In one implementation, the UE may read the value tag in Layer 1,and compare it with a value tag contained in the AAC obtained in action582. If the value tag in Layer 1 has not been changed or updated (e.g.,the value tag of the corresponding sub-categorization is the same as thevalue tag contained in the AAC obtained in action 582), then the UE mayuse the specific parameters contained in the UE specific AAC received inaction 582, instead of reading the specific parameters of thecorresponding sub-categorization in Layer 2 again. In anotherimplementation, the UE may not receive the current ACI setting in themessage containing the UE specific AAC from the base station. In suchcase, the UE still performs value tag check upon receiving Layer 1 ofthe ACI structure, but compares the value tag in Layer 1 of the ACIstructure with the value tag that the UE had previously read and stored.In both implementations described above, the UE performs value tag checkbefore requesting Layer 2 of the ACI structure. Performing the value tagcheck in action 590 may avoid unnecessary ACI reading overhead. If thevalue tag has been updated, then the UE may proceed to action 592 torequest and read updated specific parameters in Layer 2 of the ACIstructure (which may be obtained through other SI or dedicated signalingor on-demand broadcast SI or on-demand other SI).

As shown in action 594, if the UE reads and passes all the specificparameters based on the corresponding sub-categorizations, the UE may beallowed for access attempt. It is noted that, the UE should also accessthe network by following corresponding specific parameters received inLayer 2 of ACI structure. Otherwise, the UE may be assigned with abackoff time in action 596, before reading read Layer 1 of the ACIstructure again in action 586.

In action 598, once the UE is allowed to access the network, the UE mayperform access procedure with the base station. During the accessprocedure (e.g., data transmission via random access, RAN notificationarea (RNA) update) performed by the UE, the base station may alsoperform the UE's AAC configuration update. Within the access stage, thebase station can provide a new/updated UE specific AAC for performingRAN notification area update, and also can provide a UE-specific AAC forperforming data transmission via random access to the UE.

FIG. 6A is a diagram illustrating an access attempt configuration (AAC)transmission for an RRC_INACTIVE UE, according to an exemplaryimplementation of the present application. FIG. 6B is a diagramillustrating an access control information (ACI) transmission for anRRC_INACTIVE UE, according to an exemplary implementation of the presentapplication. FIGS. 6A and 6B illustrate an access control is performedby a base station (e.g., gNB) to control access of an RRC_INACTIVE UE.

As shown in FIG. 6A, during an RRC Suspend procedure, base station 604transmits an RRCConnectionRelease message to UE 602 in action 682. Inthe present implementation, the RRCConnectionRelease message contains aUE specific AAC, where the UE specific AAC is configured by base station604 and contains UE 602's access class(es) (e.g., sub-categorization)and which RACH (e.g., 2-step or 4-step or both) is allowed for UE 602for each corresponding access attempt purpose. In one implementation ofthe present application, the AAC configurations are determined by theapplication UE 602 performs and its associated QoS requirement. Inaddition, a current value tag and/or its corresponding specificparameters in Layer 2 of an ACI structure (e.g., Layer 2 of ACIstructure 400 in FIG. 4) for UE 602 can also be contained in theRRCConnectionRelease message for each access attempt purpose/category.After receiving the RRCConnectionRelease message, UE 602 transitionsinto RRC_INACTIVE state in action 683.

As shown in FIG. 6B, in action 684, UE 602 in RRC_INACTIVE state maygenerate an access attempt. In RRC_INACTIVE state, UE 602 may generatean access attempt for at least one of the following access attemptpurposes: data transmission via random access, RAN notification area(RNA) update, and RRC resume procedure.

In action 686, base station 604 may provide Layer 1 of an ACI structure(Layer 1 of ACI structure 400 in FIG. 4) to RRC_INACTIVE UE 602.RRC_INACTIVE UE 602 may check whether the access control ON/OFFindicators for its corresponding sub-categorizations are ON or OFF byreading the access control ON/OFF indicators within Layer 1 of the ACIstructure transmitted from base station 604. In the presentimplementation, UE 602 may obtain Layer 1 of the ACI structure by theminimal SI or periodically broadcasted SI. If the access control ON/OFFindicator for a corresponding sub-categorization is OFF, UE 602 may stopreading or ignore the associated control parameters within Layer 2 ofthe ACI structure. If the access control ON/OFF indicator for thecorresponding sub-categorization is OFF, UE 602 may also stop reading orignore the common parameters in Layer 1 of the ACI structure. UE 602 mayproceed to action 698 to perform access procedure. On the other hand, ifthe access control ON/OFF indicator for a correspondingsub-categorization is ON, UE 602 needs to further read the associatedcontrol parameters within Layer 2 of the ACI structure (which obtainedvia other SI or dedicated signaling or on-demand broadcast SI oron-demand other SI) to obtain all access control parameters it needs toapply.

Before UE 602 making a request to base station 604 for Layer 2 of theACI structure, UE 602 may check the value tag of correspondingsub-categorization in Layer 2 in action 690. If the value tag has notbeen changed or updated (e.g., the value tag of the correspondingsub-categorization is the same as the value tag contained in the AACobtained in action 682), UE 602 may use the UE specific AAC obtained inaction 682 which may contain UE 602's access class(es) (e.g.,sub-categorization) and which RACH (e.g., 2-step or 4-step or both) isallowed for UE 602 for each corresponding access attempt purpose. Thatis, UE 602 may use the specific parameters contained in the UE specificAAC received in action 682, instead of reading the specific parametersof the corresponding sub-categorization in Layer 2 again. Performing thevalue tag check in action 690 may avoid unnecessary ACI readingoverhead. If the value tag has been updated, then UE 602 may need torequest and read updated specific parameters in Layer 2 of the ACIstructure (which may be obtained through other SI or dedicated signalingor on-demand broadcast SI), as shown in action 692 a (e.g., UE 602requesting Layer 2 of the ACI structure through other SI request) andaction 692 b (e.g., base station 604 providing Layer 2 of the ACIstructure through other SI upon the request from UE 602, and UE 602reading Layer 2 of the ACI).

In action 694, if UE 602 passes all the specific parameters based on thecorresponding sub-categorizations, UE 602 may be allowed to access theNR network through base station 604. Otherwise, UE 602 may be assignedwith a backoff time before reading read Layer 1 of the ACI structureagain. In action 698, once UE 602 is allowed to access the NR network,UE 602 may perform access procedure with base station 604 by followingthe specific parameters in Layer 2 of the ACI structure. During theaccess procedure (e.g., data transmission via random access, RANnotification area (RNA) update) performed by UE 602, base station 604may also perform the UE's AAC configuration update. Within the accessstage, base station 604 can provide a new/updated UE specific AAC forperforming RAN notification area update, and also can provide aUE-specific AAC for performing data transmission via random access to UE602.

FIG. 7A is a diagram illustrating an access attempt configuration (AAC)transmission for an RRC_CONNECTED UE, according to an exemplaryimplementation of the present application. FIG. 7B is a diagramillustrating an access control information (ACI) transmission for anRRC_CONNECTED UE, according to an exemplary implementation of thepresent application.

As shown in FIG. 7A, UE 702 is in RRC_CONNECTED state in action 781.During an RRC Reconfiguration procedure, base station 704 transmits anRRCReconfiguration message to UE 702 in action 782. In the presentimplementation, the RRCReconfiguration message contains a UE specificAAC, where the UE specific AAC is configured by base station 704 (e.g.,gNB) and contains UE 702's access class(es) (e.g., sub-categorization).In one implementation of the present application, the AAC configurationsare determined by the application UE 702 performs and its associated QoSrequirement. In addition, a current value tag and/or its correspondingspecific parameters in Layer 2 of an ACI structure (e.g., Layer 2 of ACIstructure 400 in FIG. 4) for the RRC_CONNECTED UE 702 can also becontained in the RRCReconfiguration message for each access attemptpurpose/category.

As shown in FIG. 7B, in action 784, UE 702 in RRC_CONNECTED stategenerates an access attempt. In action 786, base station 704 may provideLayer 1 of an ACI structure (Layer 1 of ACI structure 400 in FIG. 4) toRRC_CONNECTED UE 702. RRC_CONNECTED UE 702 may check whether the accesscontrol indicators for its corresponding sub-categorizations are ON orOFF by reading the access control ON/OFF indicators within Layer 1 ofthe ACI structure transmitted from base station 704 786. In the presentimplementation, UE 702 may obtain Layer 1 of the ACI structure by theminimal SI or periodically broadcasted SI from base station 704. If theaccess control ON/OFF indicator for a corresponding sub-categorizationis OFF, UE 702 may stop reading or ignore the associated controlparameters within Layer 2 of the ACI structure. If the access controlON/OFF indicator for the corresponding sub-categorization is OFF, UE 702may also stop reading or ignore the common parameters in Layer 1 of theACI structure. UE 702 may proceed to action 798 to perform accessprocedure. On the other hand, if the access control ON/OFF indicator fora corresponding sub-categorization is ON, UE 702 needs to further readthe associated control parameters within Layer 2 of the ACI structure(which obtained via other SI or dedicated signaling or on-demandbroadcast SI or on-demand other SI) to obtain all access controlparameters it needs to apply.

Before UE 702 making a request to base station 704 for Layer 2 of theACI structure, UE 702 may check the value tag of correspondingsub-categorization in Layer 2 in action 790. If the value tag has notbeen updated (e.g., the value tag of the correspondingsub-categorization is the same as the value tag contained in the AACobtained in action 782), UE 702 may use the UE specific AAC obtained inaction 782 which contains UE 702's access class(es) (e.g.,sub-categorization). That is, UE 702 may use the specific parameterscontained in the UE specific AAC received in action 782, instead ofreading the specific parameters of the corresponding sub-categorizationin Layer 2 again. Performing the value tag check in action 790 may avoidunnecessary ACI reading overhead. If the value tag has been updated,then UE 702 may need to request and read updated specific parameters inLayer 2 of the ACI structure (which may be obtained through other SI ordedicated signaling or on-demand broadcast SI or on-demand other SI), asshown in action 792 a (e.g., UE 702 requesting Layer 2 of the ACIstructure through other SI request) and action 792 b (e.g., base station704 providing Layer 2 of the ACI structure through other SI upon therequest from UE 702, and UE 702 reading Layer 2 of the ACI).

In action 794, if UE 702 passes all the specific parameters based on thecorresponding sub-categorizations, UE 702 may be allowed to access theNR network through base station 704 by following the specific parametersin Layer 2 of ACI structure. Otherwise, UE 702 may be assigned with abackoff time before reading read Layer 1 of the ACI structure again. Inaction 798, once UE 702 is allowed to access the NR network, UE 702 mayperform access procedure with base station 704. During the accessprocedure (e.g., data transmission via random access, RAN notificationarea (RNA) update) performed by UE 702, base station 704 may alsoperform the UE's AAC configuration update. Within the access stage, basestation 704 can provide a new/updated UE specific AAC for performing RANnotification area update, and also can provide a UE-specific AAC forperforming data transmission via random access to UE 702.

FIG. 8 illustrates a block diagram of a node for wireless communication,in accordance with various aspects of the present application. In oneimplementation, node 800 may be a wireless device, such as UEs 102 a/102b, 202, 302, 602, and 702 described with respect to FIGS. 1A/1B, 2, 3,6A/6B, and 7A/7B, respectively. In another implementation, node 800 maybe a network node, such as base stations 104 a/104 b, 204, 304, 604, and704 described with respect to FIGS. 1A/1B, 2, 3, 6A/6B, and 7A/7B,respectively.

As shown in FIG. 8, node 800 may include transceiver 820, processor 826,memory 828, one or more presentation components 834, and at least oneantenna 836. Node 800 may also include an RF spectrum band module, abase station communications module, a network communications module, anda system communications management module, input/output (I/O) ports, I/Ocomponents, and power supply (not explicitly shown in FIG. 8). Each ofthese components may be in communication with each other, directly orindirectly, over one or more buses 840.

Transceiver 820 having transmitter 822 and receiver 824 may beconfigured to transmit and/or receive time and/or frequency resourcepartitioning information. In some implementations, transceiver 820 maybe configured to transmit in different types of subframes and slotsincluding, but not limited to, usable, non-usable and flexibly usablesubframes and slot formats. Transceiver 820 may be configured to receivedata and control channels.

Node 800 may include a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby node 800 and include both volatile and non-volatile media, removableand non-removable media. By way of example, and not limitation,computer-readable media may comprise computer storage media andcommunication media. Computer storage media includes both volatile andnon-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules orother data.

Computer storage media includes RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices. Computer storage media doesnot comprise a propagated data signal. Communication media typicallyembodies computer-readable instructions, data structures, programmodules or other data in a modulated data signal such as a carrier waveor other transport mechanism and includes any information deliverymedia. The term “modulated data signal” means a signal that has one ormore of its characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer-readable media.

Memory 828 may include computer-storage media in the form of volatileand/or non-volatile memory. Memory 828 may be removable, non-removable,or a combination thereof. Exemplary memory includes solid-state memory,hard drives, optical-disc drives, and etc. As illustrated in FIG. 8,memory 828 may store computer-readable, computer-executable instructions832 (e.g., software codes) that are configured to, when executed, causeprocessor 826 to perform various functions described herein, forexample, with reference to FIGS. 1 through 7B. Alternatively,instructions 832 may not be directly executable by processor 826 but beconfigured to cause node 800 (e.g., when compiled and executed) toperform various functions described herein.

Processor 826 may include an intelligent hardware device, e.g., acentral processing unit (CPU), a microcontroller, an ASIC, and etc.Processor 826 may include memory. Processor 826 may process data 830 andinstructions 832 received from memory 828, and information throughtransceiver 820, the base band communications module, and/or the networkcommunications module. Processor 826 may also process information to besent to transceiver 820 for transmission through antenna 836, to thenetwork communications module for transmission to a core network.

One or more presentation components 834 presents data indications to aperson or other device. Exemplary one or more presentation components834 include a display device, speaker, printing component, vibratingcomponent, and etc.

In accordance with implementations of the present application, an accessattempt configuration (AAC) can either configured by a base station or aUE based on a message broadcasted by the base station. The AAC maycontain information of the UE's access class, and/or ACI structure andACI's default and/or current settings. The UE access class assignmentcan be based on UE ID, QoS requirement, data size, and etc. For example,conventional access control methods can provide traffic control based onthe specific access class or application of the UEs, which arepredefined in the UEs and fixed (e.g., stored in the UEs) after themanufacturing process. A base station can deny or allow specific accessclass or application by reading it directly from the UEs. Although thisis a simple and straightforward process, this type of access controloffers no flexibility, and can result in inefficient use of radioresource in the network. By contrast, implementations of the presentapplication provide access control based on different parameters thatcan be dynamically assigned and selected.

For example, which categorization and sub-categorization(s) the UEbelongs, is determined after the UE enters the cell coverage area of thebase station. The base station determines the configuration and theparameters based on factors, such as current traffic condition. As such,the base station can dynamically assign the sub-categorization(s) forthe UE. This allows the base station to have a very small granularity.The access control method can dynamically assign radio resource based ontraffic and resource conditions, which allows the network to preserveradio resource for high priority traffic/data/application. Moreover, theACI structures according implementations of the present application arehierarchical structures. The fundamental parameters are listed inLayer 1. Layer 2 may include delta information. The base stationcontrols the ON/OFF of these parameters. For example, the base station'sloading is light, all the parameters are off. All UEs are allowedaccess. However, if the loading is heavy, the base station may configurethe layered ACI structure to determine which UEs can get access firstbased on a hierarchy. The ACI structure can allow the base station todetermine which class the UE belongs, and to decide, at any given point,which types of UEs can get access or endure the access control scheme.

From the above description it is manifest that various techniques can beused for implementing the concepts described in the present applicationwithout departing from the scope of those concepts. Moreover, while theconcepts have been described with specific reference to certainimplementations, a person of ordinary skill in the art would recognizethat changes can be made in form and detail without departing from thescope of those concepts. As such, the described implementations are tobe considered in all respects as illustrative and not restrictive. Itshould also be understood that the present application is not limited tothe particular implementations described above, but many rearrangements,modifications, and substitutions are possible without departing from thescope of the present disclosure.

The invention claimed is:
 1. A method for a wireless device to trigger aRadio Access Network (RAN) Notification Area (RNA) update while thewireless device is in a Radio Resource Control (RRC) inactive(RRC_INACTIVE) state, the method comprising: initiating an RRCresumption procedure for the RNA update; acquiring an access controlparameter configuration of an access category associated with the RNAupdate in system information block 1 (SIB1) broadcast by a network node;initiating a random access procedure for the RRC resumption procedureaccording to an indicator of the access control parameter configurationof the access category; wherein, when the indicator is OFF, theindicator indicates to the wireless device that the wireless device doesnot need to apply the access control parameter configuration of theaccess category, and that the wireless device is allowed to initiate therandom access procedure.
 2. A wireless device configured to trigger aRadio Access Network (RAN) Notification Area (RNA) update while thewireless device is in a Radio Resource Control (RRC) inactive(RRC_INACTIVE) state, the wireless device comprising: one or moreprocessors; a non-transitory machine-readable memory storing a program,the program executable by at least one of the one or more processors,the program comprising sets of instructions for: initiating an RRCresumption procedure for the RNA update; acquiring an access controlparameter configuration of an access category associated with the RNAupdate in system information block 1 (SIB1) broadcast by a network node;initiating a random access procedure for the RRC resumption procedureaccording to an indicator of the access control parameter configurationof the access category; wherein, when the indicator is OFF, theindicator indicates to the wireless device that the wireless device doesnot need to apply the access control parameter configuration of theaccess category, and that the wireless device is allowed to initiate therandom access procedure.